Greptile Summary

This PR extends the OAuth2 application consent model across all three OpenAPI 3 spec variants (client, console, server) with five new fields — tagline, tags, images, supportUrl, and dataDeletionUrl — and removes the legacy Swagger 2 specification files as part of the team's deliberate migration to an OpenAPI 3–only pipeline.

• OAuth2 consent metadata fields (tagline, tags, images, supportUrl, dataDeletionUrl) are added consistently to both the create/update request body schemas and the appwriteApplication response model, including the required array, across all three specs.
• Database model changes (console spec only): the type field is removed from the database create-request schema and the appwriteDatabase response model; default resource allocation is reduced (s-1vcpu-1gb, 1000 mCPU, 1024 MB, 10 GB storage); terminology is updated to replace "shared database" with "shared-pool database" and "type" with "node pool".
• Swagger 2 specs deleted: all three swagger2-latest-*.json files are intentionally removed, confirmed by the commit message "remove swagger 2 specs for latest".

Confidence Score: 5/5

Safe to merge — all changes are consistent across spec variants and the swagger2 removal is intentional per the commit message.

The OAuth2 metadata fields are applied uniformly across client, console, and server specs in both request schemas and the response model. The database model updates in the console spec (type removal, reduced defaults, updated descriptions) align with the terminology shift reflected in the status and specification description changes. The swagger2 file deletions are explicitly described in the commit message as intentional cleanup.

No files require special attention beyond what was already discussed in previous review threads.

Important Files Changed

_{Reviews (2): Last reviewed commit: "(chore): remove swagger 2 specs for late..." | Re-trigger Greptile}